-
Notifications
You must be signed in to change notification settings - Fork 3.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update Vamb to v4.1.3 #43684
Update Vamb to v4.1.3 #43684
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
I just noticed that the latest version in Bioconda is still 3.0.2, even though this PR was merged. Does anyone knows what might have happened? |
Could you help us with publishing the new version? @thanhleviet @jakobnissen |
I'm not sure what to do from my side |
@BiocondaBot please add label |
I think this has not been properly merged, but I posted an issue on gitter to get some help solving it. |
Looks like there was already a PR to try to fix this, but something failed. #45266 I merged master back into it since the failed build has been removed from Azure. Let's see if it can build successfully. If not, then hopefully the logs will provide some insight. |
I don't see a pycoverm on anaconda.org. Is that the right package name? If so, it would have to be added to bioconda or conda-forge. |
pycoverm is on pip (https://pypi.org/project/pycoverm/). Does it need something like below?
|
Update Vamb to v4.1.3